5.3.3 APPX Application Design Manual

- Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-1: Overview of Application Design

Terminology


There are some terms often applied to the people and systems associated with the APPX environment. The following definitions will help clarify how these terms are used as you read this manual.

An application system, or application, is a set of interrelated computer processes, data structures, and procedures designed to perform one or more business-related tasks (for instance, to produce a payroll or maintain accounts payable information).

An application designer, or designer, is a person who uses APPX to develop or modify applications that are run by end users.

An Appx Database administrator is responsible for performing filemanagement functions for the databases defined in an installation.  This person may also be responsible for the integrity of the defined data dictionaries in each application. Larger companies will have a separate database administrator to control the data dictionary, while in smaller companies this responsibility might be given to the applicationdesigner of the application.  The Appx Database Administrator is not to be confused with an RDBMS administrator.  The Appx DB Administrator only works with AppxIO files.

An Appx System administrator is responsible for installing APPX on your computer and for defining in APPX the configuration. In addition this person establishes any security controls for your applications. Therefor the system administrator requires complete access rights throughout the APPX environment.

Documentation Rights. All system administrators and application designers have the ability to change documentation, but this ability can be extended to authorized users to change the online documentation or access the Documentation Management facility.

An end user, or user, is a person who runs or executes an application written in APPX to perform a business-related task, such as preparing payroll.

The target audience for this manual is the application designer; in general, when directions or instructions are provided, they are addressed to a designer. The terms designer or end user are used only when such a distinction is essential to convey precise meaning.

Application Design Manual                                         "Powered by Appx Software"

6

©2006 By APPX Software, Inc. All Rights Reserved